Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BC-8551 - Delete const ALL_ENTITIES #5446

Open
wants to merge 103 commits into
base: main
Choose a base branch
from
Open

Conversation

CeEv
Copy link
Contributor

@CeEv CeEv commented Jan 20, 2025

Description

Each app.module should import the entities they need directly. To make dependencies explicit. The linter rules must change in a way that allow the imports.

Links to Tickets or other pull requests

JIRA :

Deployments :

Approval for review

  • DEV: If api was changed - generate-client:server was executed in vue frontend and changes were tested and put in a PR with the same branch name.
  • QA: In addition to review, the code has been manually tested (if manual testing is possible)
  • All points were discussed with the ticket creator, support-team or product owner. The code upholds all quality guidelines from the PR-template.

@bergatco bergatco changed the title BC-8551 remove all entities BC-8551 - Delete const ALL_ENTITIES Jan 23, 2025
import path from 'path';
import { ENTITIES } from './management.entity.imports';

const migrationsPath = path.resolve(__dirname, '..', '..', 'migrations', 'mikro-orm'); // TODO: Warum ist das hier überhaupt relevant?
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

// TODO: Import Reihenfolge sieht falsch aus ...IDM prüfen.
// TODO: Warum ist das hier überhaupt relevant?
Kann raus

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Imports schein richtig zu sein
Zeile 17 zeigt wo migrations Files liegen

import { createConfigModuleOptions } from '@shared/common/config-module-options';
import { ConsoleModule } from 'nestjs-console';
import path from 'path';
import { ENTITIES } from './management.entity.imports';
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hier brauchen wir alle Entities. Z.B. auch fileRecord, sollten wir aktuell eine Migration schreiben, oder eine existierende ausführen. Daher die Überlegung mit dem regex.

Comment on lines +5 to +7
import { FilesStorageClientModule } from '@infra/files-storage-client';
import { RabbitMQWrapperModule } from '@infra/rabbitmq';
import { MikroOrmModule } from '@mikro-orm/nestjs';
import { FilesStorageClientModule as FilesMetadataClientModule } from '@modules/files-storage-client';
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hier sind beide file-storage-clients drin.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ja 😭

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh neinnnnnn 😭

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants